Skip to content

Conversation

jloleysens
Copy link
Contributor

@jloleysens jloleysens commented Sep 16, 2025

@jloleysens jloleysens requested a review from a team as a code owner September 16, 2025 09:54
Copy link

github-actions bot commented Sep 17, 2025

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

edited for style and clarity. take or leave especially if I've introduced any inconsistencies.

let me know if you have any questions.

@jloleysens
Copy link
Contributor Author

Thanks for the very useful guidance @shainaraskas , I think I've addressed all of your points. Let me know what you think!

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a couple of little formatting things, along with a couple of small clarifications. looking really good + almost ready

Copy link

@rudolf rudolf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some nits to use terminology slightly closer to the Cloud configuration UI

@jloleysens
Copy link
Contributor Author

Thanks @rudolf and @shainaraskas for the feedback, I think I've addressed all of it. Let me know what you think!

Copy link
Collaborator

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

couple little bits of feedback for polish. approving to unblock, but I suggest at least altering the heading levels in "Advanced scaling using stack monitoring metrics" before shipping.

| 50 | 5 vCPU | 10GB | • {{kib}} size per zone of 16GB RAM and 8 vCPU in 1 availability zone (creates 2 x 8GB nodes)<br><br>• {{kib}} size per zone of 8GB RAM and up to 8 vCPU across 2 availability zones<br><br>• {{kib}} size per zone of 4GB RAM and up to 8 vCPU across 3 availability zones |
| 100 | 10 vCPU | 20GB | • {{kib}} size per zone of 24 GB RAM and 12 vCPU in 1 availability zone (creates 3 x 8GB nodes)<br><br>• {{kib}} size per zone of 8GB RAM and up to 8 vCPU across 3 availability zones<br><br>|

## Adjust resource allocations for {{kib}}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest moving this down after the "advanced" case because the first sentence of the "advanced" case is "building on the simple strategy ..." so the flow is kind of broken

to make it visible, you could xref it from the two scaling approach sections, like "After you determine the necessary sizing for {{kib}}, change its allocated resources."

@jloleysens jloleysens merged commit 5ecb93b into elastic:main Sep 23, 2025
7 checks passed
@jloleysens jloleysens deleted the kibana-ui-scaling-guide branch September 23, 2025 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants